Telemetry hub

ABSTRACT

Novel tools and techniques are provided for implementing a telemetry hub, and, more particularly, to methods, systems, and apparatuses for implementing a telemetry hub that obtains sensor data from a plurality of sources and that determines one or more first actions to take in response to receiving the first sensor data. In operation, a telemetry hub might receive first sensor data from one or more sensors. The telemetry hub may determine whether the first sensor data can be trusted and whether the first sensor data is valid. Based on a determination that the first sensor data can be trusted and is valid, the telemetry hub might analyze the first sensor data to determine one or more first actions to take. The telemetry hub might then implement the one or more first actions based at least in part on the analysis of the first sensor data.

COPYRIGHT STATEMENT

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

FIELD

The present disclosure relates, in general, to methods, systems, andapparatuses for implementing a telemetry hub, and, more particularly, tomethods, systems, and apparatuses for implementing a telemetry hub thatobtains sensor data from a plurality of sources and that determines oneor more first actions to take in response to receiving the first sensordata from the plurality of sources.

BACKGROUND

In conventional systems, information or data from devices or fromlogging or record systems might be received by data disseminationsystems or data collection systems. Such information or data, however,may be susceptible to interception by nefarious parties and/or spoofingby such parties, thus resulting in information or data that isunreliable or untrustworthy, especially where such information or datamay be relied upon for predicting equipment failure. Further, theinformation or data is not obtained from a plurality of sources and theinformation or data is not analyzed to determine one or morerelationships between the data obtained from a plurality of sources.

Hence, there is a need for more robust and scalable solutions forimplementing a telemetry hub, and, more particularly, to methods,systems, and apparatuses for implementing a telemetry hub that obtainssensor data from a plurality of sources and that determines one or morefirst actions to take in response to receiving the first sensor datafrom the plurality of sources.

BRIEF DESCRIPTION OF THE DRAWINGS

A further understanding of the nature and advantages of particularembodiments may be realized by reference to the remaining portions ofthe specification and the drawings, in which like reference numerals areused to refer to similar components. In some instances, a sub-label isassociated with a reference numeral to denote one of multiple similarcomponents. When reference is made to a reference numeral withoutspecification to an existing sub-label, it is intended to refer to allsuch multiple similar components.

FIG. 1 is a schematic diagram illustrating a system for implementing atelemetry hub that obtains sensor data from a plurality of sources, inaccordance with various embodiments.

FIG. 2 is a schematic diagram illustrating an example of a blockchainthat may be used by a system that utilizes blockchains to determinewhether sensor data can be trusted, in accordance with variousembodiments.

FIG. 3 is a schematic diagram illustrating another system forimplementing a telemetry hub that obtains sensor data from a pluralityof sources, in accordance with various embodiments.

FIG. 4 is a schematic diagram illustrating an embodiment of yet anothersystem for implementing a telemetry hub that obtains sensor data from aplurality of sources, in accordance with various embodiments.

FIG. 5 is a schematic diagram illustrating another embodiment of stillanother system for implementing a telemetry hub that obtains sensor datafrom a plurality of sources, in accordance with various embodiments.

FIGS. 6A-6C are flow diagrams illustrating a method for implementing atelemetry hub that obtains sensor data from a plurality of sources, inaccordance with various embodiments.

FIG. 7 is a block diagram illustrating an exemplary computer or systemhardware architecture, in accordance with various embodiments.

FIG. 8 is a block diagram illustrating a networked system of computers,computing systems, or system hardware architecture, which can be used inaccordance with various embodiments.

DETAILED DESCRIPTION OF CERTAIN EMBODIMENTS Overview

Various embodiments provide tools and techniques for implementing atelemetry hub, and, more particularly, to methods, systems, andapparatuses for implementing a telemetry hub that obtains sensor datafrom a plurality of sources and that determines one or more firstactions to take in response to receiving the first sensor data from theplurality of sources.

In various embodiments, a telemetry hub and/or computing system mightreceive first sensor data from one or more sensors associated with oneor more first user devices. In some embodiments, the telemetry huband/or the computing system may determine whether the first sensor datacan be trusted. Based on a determination that the first sensor data canbe trusted, the telemetry hub and/or the computing system may validatethe first sensor data from the one or more sensors. In some embodiments,based on a determination that the first sensor data is valid, thetelemetry hub and/or the computing system might also analyze the firstsensor data to determine one or more first actions to take in responseto receiving the first sensor data from the one or more user devices.Next, the telemetry hub and/or the computing system might implement theone or more first actions based at least in part on the analysis of thefirst sensor data.

The telemetry hub allows users to leverage one or more sensors containedwithin one or more user devices. The sensor data provided by the one ormore sensors may then be used by one or more clients to developapplications and services for one or more customers. The telemetry hubmay be used to provide a central location to obtain sensor data from oneor more users within a particular geographic area and distribute thisinformation to one or more clients and/or one or more customers.

The various embodiments described herein utilize the functionalities,advantages, and features of blockchain systems to make such informationor data more secure and more transparently reliable due to the inherentvalidation capabilities of blockchain ledgers or the like, and theinherent capabilities of blockchain systems to clearly prevent covertreplacement or modification of information contained in the blocks ofthe blockchain. The various embodiments might also utilize theblockchain system to perform data and/or source validation on data fromequipment, where such data, once validated, might be used for performingequipment failure prediction.

The following detailed description illustrates a few exemplaryembodiments in further detail to enable one of skill in the art topractice such embodiments. The described examples are provided forillustrative purposes and are not intended to limit the scope of theinvention.

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the described embodiments. It will be apparent to oneskilled in the art, however, that other embodiments of the presentinvention may be practiced without some of these specific details. Inother instances, certain structures and devices are shown in blockdiagram form. Several embodiments are described herein, and whilevarious features are ascribed to different embodiments, it should beappreciated that the features described with respect to one embodimentmay be incorporated with other embodiments as well. By the same token,however, no single feature or features of any described embodimentshould be considered essential to every embodiment of the invention, asother embodiments of the invention may omit such features.

Unless otherwise indicated, all numbers used herein to expressquantities, dimensions, and so forth used should be understood as beingmodified in all instances by the term “about.” In this application, theuse of the singular includes the plural unless specifically statedotherwise, and use of the terms “and” and “or” means “and/or” unlessotherwise indicated. Moreover, the use of the term “including,” as wellas other forms, such as “includes” and “included,” should be considerednon-exclusive. Also, terms such as “element” or “component” encompassboth elements and components comprising one unit and elements andcomponents that comprise more than one unit, unless specifically statedotherwise.

Various embodiments described herein, while embodying (in some cases)software products, computer-performed methods, and/or computer systems,represent tangible, concrete improvements to existing technologicalareas, including, without limitation, named data system technologies,data logging technologies, data request and retrieval technologies, datacollection technologies, and/or the like. In other aspects, certainembodiments, can improve the functioning of user equipment or systemsthemselves (e.g., named data systems, data logging systems, data requestand retrieval systems, data collection systems, etc.), for example, byreceiving, with a telemetry hub, first sensor data from one or moresensors associated with one or more first user devices; determining,with a computing system, whether the first sensor data can be trusted;based on a determination that the first sensor data can be trusted,validating, with the computing system, the first sensor data from theone or more sensors; based on a determination that the first sensor datais valid, analyzing, with the computing system, the first sensor data todetermine one or more first actions to take in response to receiving thefirst sensor data from the one or more user devices; and implementing,with the computing system, the one or more first actions based at leastin part on the analysis of the first sensor data; and/or the like.

In particular, to the extent any abstract concepts are present in thevarious embodiments, those concepts can be implemented as describedherein by devices, software, systems, and methods that involve specificnovel functionality (e.g., steps or operations), such as, utilizing thefunctionalities, advantages, and features of the telemetry hub to makeinformation or data that is output from one or more user devices moresecure and more accessible to one or more client devices, and/or thelike, to name a few examples, that extend beyond mere conventionalcomputer processing operations. These functionalities can producetangible results outside of the implementing computer system, including,merely by way of example, providing a more secure system for collection,logging, and transfer of data that is output from equipment, performingdata and/or source validation on such data; resulting in information ordata that is more reliable and more trustworthy, and/or the like, atleast some results of which may be observed or measured by customersand/or service providers.

In an aspect, a method might comprise receiving, with a telemetry hub,first sensor data from one or more sensors associated with one or morefirst user devices; determining, with a computing system, whether thefirst sensor data can be trusted; based on a determination that thefirst sensor data can be trusted, validating, with the computing system,the first sensor data from the one or more sensors; based on adetermination that the first sensor data is valid, analyzing, with thecomputing system, the first sensor data to determine one or more firstactions to take in response to receiving the first sensor data from theone or more user devices; and implementing, with the computing system,the one or more first actions based at least in part on the analysis ofthe first sensor data.

In some embodiments, the telemetry hub might include the computingsystem. The computing system might comprise, without limitation, one ofa data collection system, a real-time processing system, an artificialintelligence (“AI”) system, a server computer, a cloud-based computingsystem over a network, or a distributed computing system, and/or thelike. In some cases, the one or more first user devices might includeone or more network nodes, one or more service provider devices, one ormore laptop computers, one or more desktop computers, one or more tabletcomputers, one or more television sets, one or more smart televisions,one or more media players, one or more gaming consoles, one or moreset-top boxes (“STBs”), one or more digital video recording (“DVR”)devices, one or more smart phones, one or more mobile phones, or one ormore personal digital assistants, and/or the like. According to someembodiments, the one or more sensors might comprise one or moreaccelerometers, one or more thermometers, one or more air flow sensors,one or more light sensors, one or more wind sensors, one or more weatherstation sensors, one or more wave sensors, one or more motion detectors,one or more humidity sensors, one or more smoke detectors, one or moregas detection sensors, one or more biometric sensors, one or more healthsensors, one or more heartbeat sensors, one or more impact sensors, oneor more cameras, or one or more location sensors, and/or the like.

Merely by way of example, in some cases, the method might furthercomprise based on a determination that the first sensor data requiresfurther analysis to determine whether the first sensor data can betrusted, sending, with the computing system and to a blockchain system,a request for identifying a blockchain containing a block containing acopy of the first sensor data that is output by the one or more firstuser devices. In some instances, the method might further includeanalyzing, with at least one of the computing system or the blockchainsystem, the first sensor data by performing source identification on thefirst sensor data. The first sensor data might include sourceidentification information and performing source validation on the firstsensor data might include validating the source identificationinformation contained in the first sensor data.

In some cases, analyzing, with the computing system, the first sensordata to determine one or more first actions to take in response toreceiving the first sensor data from the one or more user devices mightinclude analyzing, with the computing system, the first sensor data inreal-time or near-real-time.

According to some embodiments, analyzing the first sensor data mightfurther include determining, with the computing system, a geographiclocation associated with the first sensor data; and based on adetermination of the geographic location associated with the firstsensor data, determining one or more second actions to take in responseto receiving the first sensor data from the geographic location.

The first sensor data might include, without limitation, at least one ofdata communicated by third party service provider systems, datacommunicated by public service systems, or public data, wherein the datacommunicated by public service systems comprises at least one of datacommunicated by transportation systems, data communicated by deliverysystems, or data communicated by emergency response systems, and whereinthe public data comprises at least one of data communicated by weathersystems, data communicated by user devices, or data communicated bytraffic systems, and/or the like.

In some embodiments, the first data might comprise at least one of oneor more portions of a log of interactions between a user and a serviceprovider, data communicated by third party service provider systems,data communicated by public service systems, or public data, and/or thelike. The interactions between the user and the service provider mightcomprise at least one of online chats, text messages, telephoneconversations, e-mail communications, software application usage, orservice provider website interaction by the user, and/or the like. Thepublic data might comprise at least one of weather data, stock data,news data, or street traffic data, and/or the like.

In various instances, the one of more first actions might includeidentifying, with the computing system, at least one user to receive thefirst sensor data; and sending, with the computing system, the firstsensor data to one or more second user devices associated with the atleast one user identified by the computing system.

Additionally and/or alternatively, the one or more first actions mightinclude determining, with the computing device, whether the first sensordata from the at least one first user device is related to second sensordata from at least one second device; and based on a determination thatthe first sensor data from the at least one first user device is relatedto the second sensor data from the at least one second device,associating, with the computing system, the first sensor data from theat least one device with the second sensor data from the at least onesecond device. The first sensor data may be associated with the secondsensor data based on a common geographic location associated with thefirst sensor data and the second sensor data. The method might furtherinclude generating, with the computing system, a profile with the firstsensor data and the second sensor data; and displaying, with thecomputing system, the profile with the first sensor data and the secondsensor data on a user device. The profile may display at least one ofvehicle traffic in one or more geographic locations, pedestrian trafficin one or more geographic locations, one or more obstacles located inone or more geographic locations, natural disasters in one or moregeographic locations, or one or more weather paths, and/or the like.

In some embodiments, the one or more first actions might includedetermining, with the computing system, a time sensitivity associatedwith the first sensor data; based on a determination that the firstsensor data is time sensitive, determining, with the computing system, afirst amount of time to store the first sensor data; and based on adetermination that the first sensor data is not time sensitive,determining, with the computing system, a second amount of time to storethe first sensor data.

In various cases, analyzing the first sensor data to determine one ormore first actions to be taken in response to receiving the first sensordata from the at least one first user device might further compriseanalyzing, with the computing system, the first sensor data to determinewhether the first sensor data comprises jerk feedback associated with aparticular geographic location; based on a determination that the firstsensor data comprises jerk feedback associated with the particulargeographic location, determining one or more second actions to be takenin response to receiving the jerk feedback from the at least one firstuser device; generating a notification indicating a geographic locationwhere the jerk feedback occurred; and sending, with the computingdevice, the notification to one or more user devices located within thegeographic location where the jerk feedback occurred.

In another aspect, an apparatus might comprise at least one processorand a non-transitory computer readable medium communicatively coupled tothe at least one processor. The non-transitory computer readable mediummight have stored thereon computer software comprising a set ofinstructions that, when executed by the at least one processor, causesthe apparatus to: receive first sensor data from one or more sensorsassociated with one or more first user devices; determine whether thefirst sensor data can be trusted; based on a determination that thefirst sensor data can be trusted, validate the first sensor data fromthe one or more sensors; based on a determination that the first sensordata is valid, analyze the first sensor data to determine one or morefirst actions to take in response to receiving the first sensor datafrom the one or more user devices; and implement the one or more firstactions based at least in part on the analysis of the first sensor data.

In yet another aspect, a system might comprise a first user device,which might comprise at least one first processor and a firstnon-transitory computer readable medium communicatively coupled to theat least one first processor. The first non-transitory computer readablemedium might have stored thereon computer software comprising a firstset of instructions that, when executed by the at least one firstprocessor, causes the first user device to: receive sensor data from oneor more sensors associated with the first user device; and send thesensor data to a telemetry hub.

The system might further comprise a telemetry hub, which might compriseat least one second processor and a second non-transitory computerreadable medium communicatively coupled to the at least one secondprocessor. The second non-transitory computer readable medium might havestored thereon computer software comprising a second set of instructionsthat, when executed by the at least one second processor, causes thetelemetry hub to: receive the first sensor data from the first userdevice; and send the first sensor data to a computing system.

The system might further comprise a computing system, which mightcomprise at least one third processor and a third non-transitorycomputer readable medium communicatively coupled to the at least onethird processor. The third non-transitory computer readable medium mighthave stored thereon computer software comprising a third set ofinstructions that, when executed by the at least one third processor,causes the computing system to: determine whether the first sensor datacan be trusted; based on a determination that the first sensor data canbe trusted, validate the first sensor data from the one or more sensors;based on a determination that the first sensor data is valid, analyzethe first sensor data to determine one or more first actions to take inresponse to receiving the first sensor data from the one or more userdevices; and implement the one or more first actions based at least inpart on the analysis of the first sensor data.

Various modifications and additions can be made to the embodimentsdiscussed without departing from the scope of the invention. Forexample, while the embodiments described above refer to particularfeatures, the scope of this invention also includes embodiments havingdifferent combination of features and embodiments that do not includeall of the above described features.

Specific Exemplary Embodiments

We now turn to the embodiments as illustrated by the drawings. FIGS. 1-8illustrate some of the features of the method, system, and apparatus forimplementing a telemetry hub, and, more particularly, to methods,systems, and apparatuses for implementing a telemetry hub that obtainssensor data from a plurality of sources and that determines one or morefirst actions to take in response to receiving the first sensor datafrom the plurality of sources, as referred to above. The methods,systems, and apparatuses illustrated by FIGS. 1-8 refer to examples ofdifferent embodiments that include various components and steps, whichcan be considered alternatives or which can be used in conjunction withone another in the various embodiments. The description of theillustrated methods, systems, and apparatuses shown in FIGS. 1-8 isprovided for purposes of illustration and should not be considered tolimit the scope of the different embodiments.

With reference to the figures, FIG. 1 is a schematic diagramillustrating a system 100 for implementing a telemetry hub 105 thatobtains sensor data from a plurality of sources and that determines oneor more first actions to take in response to receiving the first sensordata from the plurality of sources, in accordance with variousembodiments.

In the non-limiting embodiment of FIG. 1, system 100 might comprise atelemetry hub 105 and corresponding database(s) 110. In some cases,system 100 might further comprise computing system(s) 115 andcorresponding database(s) 120. The computing system(s) 115 might beseparate from or integrated into telemetry hub 105. Additionally,database(s) 120 might be separate from or integrated into database(s)110. In some embodiments, the telemetry hub 105 and/or computingsystem(s) 115 might include, without limitation, one of a datacollection system, a real-time processing system, an artificialintelligence (“AI”) system, a data dissemination system, a named datasystem, a server computer, a cloud-based computing system over anetwork, or a distributed computing system, and/or the like.

System 100 might further include one or more user devices 125 a-125 n(collectively, “user devices 125” or the like) comprising one or moresensors 130 a-130 n (collectively, “sensors 130” or the like). In somecases, the one or more user devices 125 might each include, but is notlimited to, one of a network node, a service provider device, a laptopcomputer, a desktop computer, a tablet computer, a television set, asmart television, a media player, a gaming console, a set-top box(“STB”), a digital video recording (“DVR”) device, a smart phone, amobile phone, or a personal digital assistant, and/or the like. The oneor more sensors 130 might include, without limitation, one or moreaccelerometers, one or more thermometers, one or more air flow sensors,one or more light sensors, one or more wind sensors, one or more weatherstation sensors, one or more wave sensors, one or more motion detectors,one or more humidity sensors, one or more smoke detectors, one or moregas detection sensors, one or more biometric sensors, one or more healthsensors, one or more heartbeat sensors, one or more impact sensors, oneor more cameras, or one or more location sensors, and/or the like.

System 100 might additionally include one or more client device(s) 135a-135 n (collectively, “client devices 135”), one or more networks 140,one or more caches 145, and a blockchain system 150. In some cases, theone or more client devices 135 might each include, but is not limitedto, one of a network node, a service provider device, a laptop computer,a desktop computer, a tablet computer, a television set, a smarttelevision, a media player, a gaming console, a set-top box (“STB”), adigital video recording (“DVR”) device, a smart phone, a mobile phone,or a personal digital assistant, and/or the like. The network(s) 140might communicatively couple together two or more of the telemetry hub105, computing system(s) 115, the user device(s) 125, the one or moreclient devices 135, the cache(s) 145, and the blockchain system 150.

In some embodiments, the blockchain system 150 might comprise ablockchain computing system 155, one or more networks 160, and peer datastorage systems #1 through #N 165 a-165 n (collectively, “peer datastorage systems 165,” “distributed peer data storage systems 165,” orthe like), the blockchain computing system 155 and the peer data storagesystems 165 being communicatively coupled to each other via network(s)160. Each instance of a blockchain containing a plurality of blocksmight be stored in two or more of the plurality of peer data storagesystems 165 a-165 n.

According to some embodiments, the network(s) 140 and/or 160 might eachinclude a local area network (“LAN”), including, without limitation, afiber network, an Ethernet network, a Token-Ring™ network, and/or thelike; a wide-area network (“WAN”); a wireless wide area network(“WWAN”); a virtual network, such as a virtual private network (“VPN”);the Internet; an intranet; an extranet; a public switched telephonenetwork (“PSTN”); an infra-red network; a wireless network, including,without limitation, a network operating under any of the IEEE 802.11suite of protocols, the Bluetooth™ protocol known in the art, and/or anyother wireless protocol (e.g., LTE protocol, 5G protocol, LoRa protocol,etc.); and/or any combination of these and/or other networks. In aparticular embodiment, the network(s) 140 and/or 160 might include anaccess network of the service provider (e.g., an Internet serviceprovider (“ISP”)). In another embodiment, the network(s) 140 and/or 160might include a core network of the service provider, and/or theInternet.

In operation, a telemetry hub 105 might receive a request to registerone or more user devices 125. When the telemetry hub receives therequest to register the one or more user devices 125, the telemetry hub105 may determine or identify one or more sensors 130 that areintegrated within the user devices 125. Based on a determination thatthe sensor data provided by the one or more sensors 130 can be used byone or more client devices 135, the telemetry hub 105 may register theone or more sensors 130 and/or the one or more user devices 125. A usermay register one or more sensors 130 and/or one or more user devices 125for a period of time (e.g., at least one hour, at least one day, atleast one week, at least one month, at least one year, and/or the like).Additionally and/or alternatively, a user may register one or moresensors 130 and/or one or more user devices 125 indefinitely and the oneor more sensors 130 and/or the one or more user devices 125 may stayregistered with the telemetry hub 105 until the user opts out ofproviding sensor data.

Once a first user device 125 a is registered with the telemetry hub 105,the telemetry hub 105 might receive first sensor data from one or moresensors 130 a associated with the first user device 125 a. The sensordata may be sent periodically (e.g., every few seconds, every fewminutes, hourly, daily, weekly, or monthly, etc.) by the first userdevice 125 a to the telemetry hub 105. In some cases, the sensor datamay be sent in response to a detection of an event by the first userdevice 125 a. In a non-limiting example, the first user device 125 amight detect one or more of an alarm sounding, temperature suddenlyrising, or a sudden force, etc., and might send the first sensor data inresponse to one or more of these events.

Additionally and/or alternatively, the telemetry hub 105 and/orcomputing system(s) 115 might pull the sensor data from the user device125 a periodically (e.g., every few seconds, every few minutes, hourly,daily, weekly, or monthly, etc.). In a non-limiting example, based on adetermination that an event (e.g., sports event, weather event, trafficevent, festival, concert, etc.) is occurring in a geographic area, thetelemetry hub 105 might periodically pull sensor data from one or moreuser devices 125 and/or one or more sensors 130 located in thegeographic area. In some instances, the telemetry hub 105 and/orcomputing system(s) 115 might pull the sensor data from the user device125 a in response to a request from one or more client devices 135 forsensor data. The one or more client devices 135 might request sensordata within a specific geographic region and, in response to thisrequest, the telemetry hub 105 and/or computing system(s) 115 might pullthe sensor data from the one or more devices 125 and/or one or moresensors 130 within the geographic region. The telemetry hub 105 and/orcomputing system(s) 115 might store the first sensor data in database110, database 120, and/or cache 145.

The first sensor data might include, without limitation, at least one ofdata communicated by third party service provider systems, datacommunicated by public service systems, or public data, and/or the like.The data communicated by public service systems might include at leastone of data communicated by transportation systems, data communicated bydelivery systems, or data communicated by emergency response systems,and/or the like. The public data might include, without limitation, atleast one of data communicated by weather systems, data communicated byuser devices, or data communicated by traffic systems, and/or the like.

Next, the telemetry hub 105 and/or computing system(s) 115 mightdetermine whether the first sensor data can be trusted. The telemetryhub 105 and/or computing system(s) 115 might determine whether thesensor data originated from a trusted user device 125, and/or the like.In some cases, based on a determination that the first user device 125 atypically or historically provides trusted data, the telemetry hub 105and/or computing system(s) 115 might determine that the data can betrusted.

Additionally, and/or alternatively, the telemetry hub 105 and/orcomputing system(s) 115 might send the first sensor data to blockchainsystem 150 to determine whether the first sensor data can be trusted.The telemetry hub 105 and/or computing system(s) 115 might send, to theblockchain system 150 or blockchain computing system 155, a secondrequest for identifying a blockchain (e.g., blockchain 205 of FIG. 2, orthe like) containing a block containing the first sensor data (i.e.,data that is output by the first user device 125 a, or the like). Inresponse to the blockchain system 150 or blockchain computing system 155identifying a blockchain containing a block containing the first sensordata, the telemetry hub 105, the computing system(s) 115, the blockchainsystem 150, or blockchain computing system 155 might receive a copy ofthe identified blockchain from the blockchain system 150 or blockchaincomputing system 155. The telemetry hub 105 and/or computing system(s)115 might then compare the first sensor data with the copy of theidentified blockchain to make sure that the first sensor data matchesthe copy of the identified blockchain. Based on a determination that thefirst sensor data matches the copy of the identified blockchain, thetelemetry hub 105 and/or the computing system(s) 115 might determinethat the first sensor data can be trusted.

Based on a determination that the first sensor data can be trusted, thetelemetry hub 105 and/or computing system(s) 115 might validate thefirst sensor data from the one or more sensors 130. The telemetry hub105 and/or computing system(s) 115 might determine whether the firstsensor data from the one or more sensors 130 is accurate. In order tovalidate the first sensor data, the telemetry hub 105 and/or computingsystem(s) 115 might compare the first sensor data with other sensor datawithin a geographic region and might determine whether the first sensordata matches or is close to the other sensor data within the samegeographic region. Additionally and/or alternatively, based on adetermination that the first user device 125 a typically or historicallyprovides accurate data, the telemetry hub 105 and/or computing system(s)115 might determine that the first sensor data is accurate.

In some cases, based on a determination that the first sensor data isvalid, the telemetry hub 105 and/or computing system(s) 115 mightanalyze the first sensor data to determine one or more first actions totake in response to receiving the first sensor data from the one or moreuser devices 125. The first sensor data might be analyzed in real-timeor near real-time using real-time processing systems, artificialintelligence (“AI”) systems, and/or the like. The first sensor data maybe analyzed in real-time to determine whether the telemetry hub 105and/or computing system(s) 115 needs to implement one or more actions inreal-time.

In various embodiments, the telemetry hub 105 and/or computing system(s)115 might remove private data from the first sensor data before sendingthe first sensor data to one or more client devices 135. For example,the telemetry hub 105 and/or computing system(s) 115 might remove thesource of the first sensor data, a user associated with the first sensordevice, a first user device 125 a that sent the first sensor data, anexact location associated with the sensor data, or an exact timeassociated with the first sensor data, and/or the like.

In various instances, the first sensor data may be analyzed to determinea geographic location and/or a time associated with the first sensordata. The user device 125 a may send the first sensor data with alocation stamp indicating a location where the first sensor data wasobtained and/or a time stamp indicating a time when the first sensordata was obtained. Based on a determination of the geographic locationand/or time associated with the first sensor data, the telemetry hub 105and/or computing system(s) 115 might determine one or more first actionsto take in response to receiving the first sensor data from thegeographic location and/or time.

The first sensor data might further be analyzed to determine atime-sensitivity associated with the first sensor data. For example, thetelemetry hub 105 and/or computing system(s) 115 may determine whetherto immediately implement the one or more first actions based on thefirst sensor data and/or determine whether to wait to implement the oneor more first actions based on the first sensor data.

The telemetry hub 105 and/or computing system(s) 115 may further analyzethe first sensor data to determine one or more trends (e.g., hourlytrends, daily trends, weekly trends, monthly trends, yearly trends,seasonal trends, and/or the like). The telemetry hub 105 and/orcomputing system(s) 115 might determine whether sensor data should beincluded in a short-term trend or a long-term trend. In a non-limitingexample, sensor data associated with “jerk feedback” (described in moredetail later in the specification) may be kept for a shorter period oftime and may be indicative of a shorter time period trend while weatherdata may be kept for longer to period of time and may be indicative of aseasonal trend. Based on the one or more determined trends, thetelemetry hub 105 and/or computing system(s) 115 might determine one ormore first actions to take.

The telemetry hub 105 and/or computing system(s) 115 might thenimplement the one or more first actions based at least in part on theanalysis of the first sensor data. In some cases, the telemetry hub 105and/or computing system(s) 115 might determine one or more users and/orclient devices 135 to receive the first sensor data.

The one or more users and/or client devices 135 might be registered withthe telemetry hub 105 and/or computing system(s) 115. A user mayregister one or more client devices 135 for a specific period of time(e.g., at least one hour, at least one day, at least one week, at leastone month, at least one year, and/or the like). Additionally and/oralternatively, a user may register one or more client devices 135indefinitely, and the one or more client devices 135 may stay registeredwith the telemetry hub 105 until the user opts out of providing sensordata.

Once one or more client devices 135 are registered with the telemetryhub 105, the telemetry hub 105 might receive first sensor data from oneor more sensors 130 a associated with the first user device 125 a andmight send the first sensor data to one or more client devices 135 basedon a determination that the one or more client devices 135 areinterested in the first sensor data. The sensor data may be sentperiodically (e.g., every few seconds, every few minutes, hourly, daily,weekly, monthly, etc.) by the telemetry hub 105 and/or computingsystem(s) 115 to the one or more client devices 135. In some cases, thesensor data may be sent in response to a detection of an event by thetelemetry hub 105 and/or computing system(s) 115. In a non-limitingexample, the telemetry hub 105 and/or computing system(s) 115 mightdetect one or more of an alarm sounding, temperature suddenly rising, ora sudden force, etc., and might send the first sensor data to the one ormore client devices 135 in response to one or more of these events.

In some embodiments, the one or more client devices 135 might requestsensor data within a specific geographic region and, in response to thisrequest, the telemetry hub 105 and/or computing system(s) 115 might sendthe sensor data from the one or more first user devices 125 within thegeographic region to the requesting one or more client devices 135.

In some instances, the one or more first actions might includedetermining, with the telemetry hub 105 and/or the computing device 115,whether the first sensor data from the at least one first user device125 a is related to second sensor data from at least one second userdevice 125 b (not shown). Based on a determination that the first sensordata from the first user device 125 a is related to the second sensordata from the second user device 125 b, the telemetry hub 105 and/orcomputing system(s) 115 might (1) remove redundant sensor data, (2)determine whether one or more patterns or trends exist between the firstsensor data and the second sensor data; (3) validate the first sensordata with the second sensor data; and/or (4) associate the first sensordata with the second sensor data, and/or the like. The first sensor datamay be associated with the second sensor data based on a commongeographic location associated with the first sensor data and the secondsensor data and/or a common time associated with the first sensor dataand the second sensor data.

The telemetry hub 105 and/or computing system(s) 115 might generate aprofile with the first sensor data and the second sensor data and mightdisplay the profile with the first sensor data and the second sensordata on one or more requesting client devices 135. The profile mightdisplay, without limitation, at least one of vehicle traffic in one ormore geographic locations, pedestrian traffic in one or more geographiclocations, one or more obstacles located in one or more geographiclocations, natural disasters in one or more geographic locations, or oneor more weather paths, and/or the like.

In some instances, the one or more actions might include determining,with the telemetry hub 105 and/or the computing system(s) 115, a timesensitivity associated with the first sensor data. Based on adetermination that the first sensor data is time sensitive, thetelemetry hub 105 and/or the computing system(s) 115 might determine afirst amount of time to store the first sensor data. For example, if thefirst sensor data is time sensitive (e.g., real-time information such astraffic data, and/or the like), the first sensor data may only be storedfor a short period of time because the first sensor data is onlyrelevant for a short period of time. Based on a determination that thefirst sensor data is not time sensitive, the telemetry hub 105 and/orthe computing system(s) 115 might determine a second amount of time tostore the first sensor data. For example, if the first sensor data isnot time sensitive (e.g., seasonal information such as weather data,and/or the like), the first sensor data may be stored for a longerperiod of time to determine seasonal information, yearly information,and/or the like. The first sensor data may be stored using blockchainsystem 150 to ensure that the first sensor data is trustworthy.

These and other functionalities of the various embodiments are describedin detail below with respect to FIGS. 2-6.

FIG. 2 is a schematic diagram illustrating an example 200 of ablockchain that may be used by a system that utilizes blockchains todetermine whether sensor data can be trusted, in accordance with variousembodiments.

With reference to FIG. 2, an example 200 of a blockchain 205 isdepicted. Blockchain 205 might comprise a plurality of blocks 210 a-210e (collectively, “blocks 210” or the like), each block 210 containingone or more source fields #1-#4 215 and/or one or more data fields #1-#4220. The source fields 215 might each contain information regarding asource corresponding to data (e.g., source field #1 might correspond todata field #1, and so on). For purposes of simplicity of illustration,only five blocks 210 are shown in the blockchain 205 in FIG. 2, althoughblockchain 205 might comprise any suitable number of blocks 210.Although only four source fields 215 are shown in each block 210, thevarious embodiments are not so limited, and blockchains 205 mightcontain any suitable number of source fields 215. Similarly, althoughonly four data fields 220 are shown in each block 210, the variousembodiments are not so limited, and blockchains 205 might contain anysuitable number of data fields 220. Although not shown, each block 210might also contain other data or fields, including, but not limited to,block number fields, nonce field, location fields, data and/or timestamp fields, previous hash field, hash field, and/or the like. Asdescribed herein with respect to FIGS. 1 and 3-6, source identificationmay be performed on the data contained in the source fields 215, whiledata validation may be performed on the data contained in the datafields 220.

FIG. 3 is a schematic diagram illustrating another system 300 forimplementing a telemetry hub 305 that obtains sensor data from aplurality of sources, in accordance with various embodiments. System 300represents a portion of system 100.

System 300 might comprise a telemetry hub 305 (which may correspond totelemetry hub 105 of FIG. 1, or the like) and a correspondingdatabase(s) 310 (which may correspond to database(s) 110 of FIG. 1, orthe like). System 300 might further include a computing system(s) 315(which may correspond to computing system(s) 115 of FIG. 1, or the like)and a corresponding database(s) 320 (which may correspond to database(s)120 of FIG. 1, or the like). System 300 might additionally include oneor more user devices 325 a-325 n (which may correspond to one or moreuser devices 125 a-125 n of FIG. 1, or the like) and corresponding oneor more sensors 330 a-330 n (which may correspond to one or more sensors130 a-130 n of FIG. 1, or the like). System 300 might also include oneor more client devices 335 a-335 n (which may correspond to one or moreclient devices 135 a-135 n of FIG. 1, or the like), one or more networks340 (which may correspond to one or more networks 140 of FIG. 1, or thelike), and one or more geographic regions 345 a-345 n. The one or moregeographic regions 345 a-345 n may be different geographic regions.

In operation, a telemetry hub 305 and/or computing system(s) 315 mightreceive first sensor data from one or more sensors 330 associated withone or more first user devices 325. The first sensor data might have atleast one of a geographic location and/or time stamp associated with thefirst sensor data. Additionally and/or alternatively, the telemetry hub305 and/or computing system(s) 315 might pull the sensor data from theone or more first user devices 325 a based on a determination that anevent (e.g., sports event, weather event, traffic event, festival,concert, etc.) is occurring at a specific time and/or in a specificgeographic region 345 a. In some instances, the telemetry hub 305 and/orcomputing system(s) 315 might pull the sensor data from the one or moreuser devices 325 a in response to a request from one or more clientdevices 335 for sensor data. The one or more client devices 335 a mightrequest sensor data within a specific geographic region 345 a and, inresponse to this request, the telemetry hub 305 and/or computingsystem(s) 315 might pull the sensor data from the one or more userdevices 325 a within the geographic region 345 a. The telemetry hub 305and/or computing system(s) 315 might store the first sensor data indatabase(s) 310 and/or database(s) 320.

The telemetry hub 305 and/or computing system(s) 315 might validate thefirst sensor data from the one or more sensors 330. The telemetry hub305 and/or computing system(s) 315 might determine whether the firstsensor data from the one or more sensors 330 is accurate. In order tovalidate the first sensor data, the telemetry hub 305 and/or computingsystem(s) 315 might compare the first sensor data with other sensor datawithin a geographic region 345 a and might determine whether the firstsensor data matches or is close to the other sensor data within the samegeographic region 345 a.

In some cases, based on a determination that the first sensor data isvalid, the telemetry hub 305 and/or computing system(s) 315 mightanalyze the first sensor data to determine one or more first actions totake in response to receiving the first sensor data from the one or moreuser devices 325. The first sensor data might be analyzed in real-timeor near real-time using real-time processing systems, artificialintelligence (“AI”) systems, and/or the like. The first sensor data maybe analyzed in real-time to determine whether the telemetry hub 305and/or computing system(s) 315 needs to implement one or more actions inreal-time or near real-time.

In various instances, the first sensor data may be analyzed to determinea geographic region 345 a and/or a time associated with the first sensordata. The user device 325 a may send the first sensor data with alocation stamp indicating a location where the first sensor data wasobtained and/or a time stamp indicating a time when the first sensordata was obtained. Based on a determination of the geographic location345 a and/or time associated with the first sensor data, the telemetryhub 305 and/or computing system(s) 315 might determine one or more firstactions to take in response to receiving the first sensor data from thegeographic location and/or time.

The telemetry hub 305 and/or computing system(s) 315 might thenimplement the one or more first actions based at least in part on theanalysis of the first sensor data. In some cases, the telemetry hub 305and/or computing system(s) 315 might determine one or more users and/orclient devices 335 to receive the first sensor data.

Once one or more client devices 335 are registered with the telemetryhub 305, the telemetry hub 305 may receive first sensor data from one ormore sensors 330 a associated with the first user device 325 a and maysend the first sensor data to one or more client devices 335 a based ona determination that the one or more client devices 335 a are interestedin the first sensor data. The sensor data may be sent periodically(e.g., every few seconds, every few minutes, hourly, daily, weekly,monthly, etc.) by the telemetry hub 305 and/or computing system(s) 315to the one or more client devices 335 a. In some cases, the sensor datamay be sent in response to a detection of an event by the telemetry hub305 and/or computing system(s) 315 within geographic region 345 a. In anon-limiting example, the telemetry hub 305 and/or computing system(s)315 might detect one or more of an alarm sounding, temperature suddenlyrising, or a sudden force, etc., and might send the first sensor data tothe one or more client devices 335 a in response to one or more of theseevents.

In some embodiments, the one or more client devices 335 might requestsensor data within a specific geographic region 345 a and, in responseto this request, the telemetry hub 305 and/or computing system(s) 315might send the sensor data from the one or more first user devices 325 awithin the geographic region 345 a to the one or more requesting clientdevice 335 a.

In some instances, the one or more first actions might includedetermining, with the telemetry hub 305 and/or the computing system(s)315, whether the first sensor data from the at least one first userdevice 325 a is related to second sensor data from at least one seconduser device 325 b. Based on a determination that the first sensor datafrom the first user device 325 a is related to the second sensor datafrom the second user device 325 b, the telemetry hub 305 and/orcomputing system(s) 315 might (1) remove redundant sensor data, (2)determine whether one or more patterns or trends exist between the firstsensor data and the second sensor data; (3) validate the first sensordata with the second sensor data; and/or (4) associate the first sensordata with the second sensor data, and/or the like. The first sensor datamay be associated with the second sensor data based on a commongeographic location associated with the first sensor data and the secondsensor data and/or a common time associated with the first sensor dataand the second sensor data.

The telemetry hub 305 and/or computing system(s) 315 might generate aprofile with the first sensor data and the second sensor data and mightdisplay the profile with the first sensor data and the second sensordata on one or more requesting client devices 335. The profile mightdisplay, without limitation, at least one of vehicle traffic in one ormore geographic locations, pedestrian traffic in one or more geographiclocations, one or more obstacles located in one or more geographiclocations, natural disasters in one or more geographic locations, or oneor more weather paths, and/or the like.

In some instances, the one or more actions might include determining,with the telemetry hub 305 and/or the computing system(s) 315, a timesensitivity associated with the first sensor data. Based on adetermination that the first sensor data is time sensitive, thetelemetry hub 305 and/or the computing system(s) 315 might determine afirst amount of time to store the first sensor data. For example, if thefirst sensor data is time sensitive (e.g., real-time information such astraffic data, jerk feedback data, and/or the like), the first sensordata may only be stored for a short period of time because the firstsensor data is only relevant for a short period of time. Based on adetermination that the first sensor data is not time sensitive, thetelemetry hub 305 and/or the computing system(s) 315 might determine asecond amount of time to store the first sensor data. For example, ifthe first sensor data is not time sensitive (e.g., seasonal informationsuch as weather data, and/or the like), the first sensor data may bestored for a longer period of time to determine seasonal information,yearly information, and/or the like. The first sensor data may be storedusing a blockchain system to ensure that the first sensor data istrustworthy.

FIG. 4 is a schematic diagram illustrating a system 400 for implementinga telemetry hub 405 that obtains sensor data from a plurality of sourcesand that determines one or more first actions to take in response toreceiving the first sensor data from the plurality of sources, inaccordance with various embodiments.

In FIG. 4, system 400 might comprise one or more telemetry hubs 405, oneor more sensors 410, and/or one or more user devices 415, each of whichmight communicate with each other via machine-to-machine communicationsand/or via one or more networks.

The one or more telemetry hubs 405 might include, without limitation, atleast one of a central node 405 a (or a single processor or a pluralityof processors disposed therein, where such processor or processors maybe physical or virtual in nature) located within a service providernetwork, a management node 405 b that may be located within at least aportion of a population area, a roadway, and/or the like, and/or othercomputing systems 405 c, which might include, but are not limited to, amanagement node that may be located at a service provider facilityassociated with a service provider that provides services to at leastportions of the population area, a management node located at a customerpremises, one or more roadway-embedded management nodes, one or moremunicipal, state, federal, or private entity management nodes, acomputing system disposed at a vehicle traffic control center, a servercomputer that serves the population area, a server computer that isremote from the population area, a cloud computing system, a distributedcomputing system that integrates computing resources from two or moredevices, or a combination of two or more of these computing systems,and/or the like

According to some embodiments, the one or more sensors 410 mightinclude, without limitation, one or more household sensors 410 a, one ormore vehicular sensors 410 b, one or more utility sensors 410 c, one ormore road sensor(s) 410 d, one or more city sensor(s) 410 e, one or moresensors associated with one or more emergency responders 410 f, one ormore other sensor(s) 410 g, and/or the like.

The one or more household sensor(s) 410 a might include at least one ofone or more temperature sensors (e.g., heat sensors, infrared sensors,thermometers, etc.), one or more light sensors (e.g., ambient lightsensors, luminosity sensors, illuminance sensors, solar light sensors,etc.), one or more humidity sensors, one or more motion sensors, one ormore cameras, one or more biometric sensors, one or more health sensors(e.g., fitness tracker, heart rate sensor, etc.), one or more locationsensors (e.g., global positioning system (“GPS”) devices, globalnavigation satellite system (“GNSS”) devices, other location sensors,etc.), one or more air quality sensors, one or more carbon monoxidesensors, one or more smoke detectors, one or more gas detectors, one ormore water leak detectors, one or more contact sensors, one or moreaudio sensors, one or more accelerometers, one or more proximitysensors, one or more radiation sensors, one or more telecommunicationssignal sensors, and/or the like. In some embodiments, the householdsensors 410 a might further include, without limitation, one or morethermometers in one or more rooms of the customer premises, one or moreinfrared (“IR”) thermometers aimed at one or more positions in the oneor more rooms, one or more air flow sensors in the one or more rooms,one or more air flow sensors in air ducts directed toward the one ormore rooms, one or more indoor solar light sensors, one or more outdoorsolar light sensors, one or more outdoor wind sensors, one or moreneighborhood weather station sensors, one or more regional weatherstation sensors, one or more motion detectors detecting presence ofpeople or animals in at least one of the one or more rooms or outsidethe customer premises, one or more humidity sensors in the one or morerooms, one or more smoke detectors detecting smoke in the one or morerooms, one or more gas detection sensors detecting gas in the one ormore rooms, one or more biometric sensors identifying at least oneperson, or one or more health sensors detecting health information forat least one person, and/or the like.

The one or more vehicle sensors 410 b might be associated with at leastone of one or more vehicles associated with a customer premises, one ormore vehicles associated with an emergency responder, one or morevehicles located on a roadway, and/or the like. The one or more vehiclesensors 410 b might include, without limitation, one or more temperaturesensors (e.g., heat sensors, infrared sensors, thermometers, etc.), oneor more light sensors (e.g., ambient light sensors, luminosity sensors,illuminance sensors, solar light sensors, etc.), one or more proximitysensors (e.g., vehicle camera-based collision avoidance system, thevehicle radar-based proximity detection system, the vehicle lidar-basedproximity detection system, the vehicle sonar-based proximity detectionsystem, etc.), one or more speed sensors, one or more cameras, one ormore fuel level sensors (e.g., gasoline tank level sensors, diesel tanklevel sensors, battery charge level sensors, etc.), one or more locationsensors (e.g., global positioning system (“GPS”) devices, globalnavigation satellite system (“GNSS”) devices, other location sensors,etc.), one or more brake sensors, one or more air quality sensors, oneor more carbon monoxide sensors, one or more smoke detectors, one ormore fluid leak detectors, one or more contact sensors (e.g., for thedoor lock system, the hood ajar detector, the trunk ajar detector, themoon/sky light ajar detector, the window open detector, and/or thelike), one or more audio sensors, one or more accelerometers, one ormore telecommunications signal sensors, one or more tire pressuresensors, an engine temperature sensor, one or more fluid leak detectors,one or more occupant sensors, one or more impact sensors, one or morestress sensors, or one or more suspension system diagnostic sensors,and/or the like.

The one or more utility sensors 410 c may include, without limitation,one or more gas detection sensors, one or more water detection sensors,one or more gas flow rate sensors, one or more water flow rate sensors,and/or the like.

The one or more road sensor(s) 410 d might include, without limitation,one or more temperature sensors (e.g., heat sensors, infrared sensors,thermometers, etc.), one or more light sensors (e.g., ambient lightsensors, luminosity sensors, illuminance sensors, solar light sensors,etc.), one or more humidity sensors, one or more motion sensors, one ormore structural integrity sensors, one or more pressure sensors, one ormore air quality sensors, one or more communications signal detectors,one or more seismic sensors, one or more weather station sensors, one ormore moisture sensors, one or more wind sensors, one or more particulatesensors, one or more impact sensors, one or more stress sensors, or oneor more location sensors, and/or the like.

The one or more city sensors 410 e may include, without limitation, oneor more temperature sensors (e.g., heat sensors, infrared sensors,thermometers, etc.), one or more light sensors (e.g., ambient lightsensors, luminosity sensors, illuminance sensors, solar light sensors,etc.), one or more weather sensors, one or more motion sensors, one ormore structural integrity sensors, one or more pressure sensors, one ormore air quality sensors, one or more communications signal detectors,one or more seismic sensors, one or more weather station sensors, one ormore moisture sensors, one or more humidity sensors, one or more windsensors, one or more particulate sensors, one or more impact sensors, orone or more location sensors, and/or the like. In some instances, theone or more city sensors 410 e might further comprise sensors in each ofone or more vehicles travelling on the roadway. In some cases, the oneor more structural integrity sensors might include, without limitation,at least one of two or more global positioning system sensors or two ormore relative position sensors that are embedded in or disposed on oneor more exterior surfaces of at least one of portions of one or moreroadways (including, but not limited to, at least one of a local road, amain road, a highway, an airport apron, an airport ramp, an airportrunway, a canal, a lock, or a waterway, and/or the like), portions ofone or more public pathways (e.g., sidewalks, trails, public movingpathways, public escalators, public elevators, etc.), portions of one ormore buildings (e.g., government buildings, other public buildings,etc.), portions of one or more public centers, portions of one or moreairport terminal buildings, portions of one or more airport hangars andservice buildings, portions of one or more railway facilities, portionsof one or more railway tracks, portions of one or more marine ports,portions of one or more public transit structures, portions of one ormore utility structures, portions of one or more public monuments orpublic art pieces, bridges, tunnels, and/or the like, where the sensordata from these sensors might comprise data indicating a change inposition of one structural integrity sensor relative to anotherstructural integrity sensor beyond a predetermined threshold amount,thereby indicating that there might be damage to corresponding at leastone of one or more roadways, one or more public pathways, one or morebuildings, one or more public centers, one or more airport terminalbuildings, one or more airport hangars and service buildings, one ormore railway facilities, one or more railway tracks, one or more marineports, one or more public transit structures, one or more utilitystructures, one or more public monuments or public art pieces, bridges,tunnels, and/or the like.

The one or more emergency responder sensor(s) 410 f may be associatedwith one or more emergency responders responding to an emergencysituation. The one or more emergency responder sensor(s) 410 f, mayinclude, without limitation, one or more biometric sensors (e.g.,fingerprint sensors, palm print sensors, footprint sensors, handprintsensors, voice identification sensors, iris scanners, retina scanners,etc.), one or more health sensors (e.g., heart rate monitors,respiratory monitors, etc.) one or more locations sensors (e.g., globalpositioning system (“GPS”) devices, global navigation satellite system(“GNSS”) devices, other location sensors, etc.), and/or the like.

In some embodiments, the household devices 415 a might include one ormore household sensors 410 a and/or might further include, withoutlimitation, a desktop computer, a laptop computer, a tablet computer, asmart phone, a mobile phone, a portable gaming device, a database ordata storage device, a network access point (“NAP”), a television ormonitor, a set-top box (“STB”), a gaming console, an image capturedevice, a video capture device, a time piece (including, withoutlimitation, a clock, a watch, or other time piece, and the like), athermostat or environmental control system, a kitchen appliance(including, but not limited to, a microwave oven, a refrigerator, anoven, a range, a stove, an induction cooktop, a pressure cooker, a ricecooker, a bread maker, a coffee machine, a kettle, a dishwasher, a foodthermometer, and/or the like), a medical device, a telephone system, aspeaker, a media recording and/or playback device, a lighting system, acustomer premises security control system, one or more dedicated remotecontrol devices, one or more universal remote control devices, apersonal digital assistant, a fitness tracking device, a printer, ascanner, an image projection device, a video projection device, ahousehold appliance, a vehicle, an audio headset, earbuds, virtualreality goggles or headset, augmented reality goggles or headset, a doorunlocking/locking system, an automated door opening/closing system, awindow locking system, an automated window opening or closing system, anautomated window covering control system, a smart window, a solar cellor solar cell array, an electrical outlet or smart node, a power stripor bar, a dimmer switch, a data port, a sprinkler system, exerciseequipment, and/or the like. The household devices 415 a might furtherinclude, but are not limited to, one or more of a furnace, an airconditioner, one or more automated skylight opening or closing systems,one or more humidifiers, one or more dehumidifiers, one or moreventilation fans, one or more automated lawn mowers, one or moreautomated trimmers, one or more sprinkler systems, one or morefertilizer dispensers, one or more animal deterrent systems, one or moreautomated snow shovels, one or more automated snow blowers, one or moreanimal deterrent systems, one or more speakers warning people aboutmachinery in use, one or more lights or display devices warning peopleabout machinery in use, one or more de-icing machines, one or moreheating mats, one or more built-in radiant heat systems under the atleast one pathway, one or more air purifiers, one or more air filters,one or more electrostatic particulate collecting tools, a washingmachine, a clothes dryer, a fire suppression system, one or moreemergency exit markers, one or more exit route markers, one or morelights (e.g., LEDs, indicator lights, warning lights, etc.), one or morefire suppression drones, one or more white noise generators, and/or thelike.

The one or more vehicular devices 415 b might be associated with atleast one of one or more vehicles associated with a customer premises,one or more vehicles associated with an emergency responder, one or morevehicles located on a roadway between one or more emergency responsevehicles and a customer premises, and/or the like. The one or morevehicular devices 415 b might include, but are not limited to, one ormore sensors 410 b and/or might further include, without limitation, avehicle computer, a vehicle engine, an electronic throttle control(“ETC”) system, a vehicle brake system, a vehicle steering system, avehicle head light system, a vehicle turn signal light system, a vehiclebrake light system, a vehicle (analog or digital) instrument gaugecluster, a vehicle heads-up-display (“HUD”) system, a vehicle-basedtransceiver or communications system, a navigation system, a vehicledisplay device, a vehicle speaker system, a vehicle (self-) diagnosticsystem, a vehicle hazard light system, a vehicle gear system, a doorunlocking/locking system, an automated door opening/closing system, anautomated window opening or closing system, an automated vehicle windowcovering control system, a data port, one or more vehicle climatecontrol systems, one or more air purifiers, one or more air filters, oneor more electrostatic particulate collecting tools, a fire suppressionsystem, one or more lights (e.g., reading lights, LEDs, indicatorlights, warning lights, etc.), or a vehicle-based wireless access point(“WAP”), and/or the like.

The one or more utility devices 415 c, might include, but are notlimited to, one or more sensors 410 c and/or might further include,without limitation, one or more electric utility devices, one or moregas utility devices, or one or more water utility devices, and/or thelike.

The one or more road device(s) 415 d, might include, but are not limitedto, one or more sensors 410 d and/or might further include, withoutlimitation, one or more power generation nodes, one or more batterycharging nodes, one or more communications systems, one or more trafficcontrol signal devices, one or more street lamps, one or more dynamiclane change markers, one or more vehicular components in each of one ormore vehicles travelling on the roadway (including, but not limited to,a vehicle computer, a vehicle engine, an electronic throttle control(“ETC”) system, a vehicle brake system, a vehicle steering system, avehicle light system, a vehicle (analog or digital) instrument gaugecluster, a navigation system, a vehicle (self-) diagnostic system, avehicle-based transceiver or communications system, and/or the like), avehicle gear system, one or more air purifiers, one or more air filters,one or more electrostatic particulate collecting tools, a firesuppression system, one or more lights (e.g., LEDs, indicator lights,warning lights, etc.), or a wireless access point (“WAP”), and/or thelike.

In some embodiments, the city devices 415 e might include one or morecity sensors 410 e and/or might further include, without limitation, oneor more power generation nodes, one or more battery charging nodes, oneor more communications systems, one or more traffic control signaldevices, one or more street lamps, one or more dynamic lane changemarkers, one or more vehicle systems or vehicular components in each ofone or more vehicles travelling on the roadway (including, but notlimited to, a vehicle computer, a vehicle engine, an electronic throttlecontrol (“ETC”) system, a vehicle brake system, a vehicle gear system, avehicle steering system, a vehicle light system, a vehicle (analog ordigital) instrument gauge cluster, a navigation system, a vehicle(self-) diagnostic system, a vehicle-based transceiver or communicationssystem, and/or the like), one or more public transit vehicle systems ineach of one or more public transit vehicles travelling on the roadway,waterway, and/or railway (including, but not limited to, a vehiclecomputer, a vehicle engine, an electronic throttle control (“ETC”)system, a vehicle brake system, a vehicle gear system, a vehiclesteering system, a vehicle light system, a vehicle (analog or digital)instrument gauge cluster, a navigation system, a vehicle (self-)diagnostic system, a vehicle-based transceiver or communications system,and/or the like), one or more public display devices (e.g., electronicbillboards, digital public signs, public televisions, public monitors,public touchscreen interface displays, public directories, and/or thelike), one or more power distribution systems, one or more railwaysystems (including, without limitation, train control systems, railwayswitch controls, railway crossing controls, rail track power systems,rail track maintenance systems such as rail lubrication systems andswitch heaters, track diagnostic systems, railway signal diagnosticsystems, and/or the like), one or more user devices associated withusers who are currently located in the population area, one or morecleaning systems, one or more grounds-keeping systems, one or moreemergency (response) systems, one or more transceivers, a wirelessaccess point (“WAP”), a door unlocking/locking system installed in oneor more public buildings or facilities, an automated dooropening/closing system installed in one or more public buildings orfacilities, an automated window opening or closing system installed inone or more public buildings or facilities, an automated window coveringcontrol system installed in one or more public buildings or facilities,a data port, one or more building climate control systems, one or morepublic transport climate control systems, one or more air purifiers, oneor more air filters, one or more electrostatic particulate collectingtools, a fire suppression system, or one or more lights (e.g., readinglights, LEDs, indicator lights, warning lights, etc.), and/or the like.

In some cases, the emergency responder device(s), might include, withoutlimitation, a desktop computer, a laptop computer, a tablet computer, asmart phone, a mobile phone, one or more personal digital assistants,one or more global positioning systems, or one or more drones, and/orthe like.

FIG. 5 is a schematic diagram illustrating a system 500 for implementinga telemetry hub 505 that obtains sensor data from a plurality of sourcesand that determines one or more first actions to take in response toreceiving the first sensor data from the plurality of sources, inaccordance with various embodiments.

With reference to FIG. 5, system 500 might comprise a city block 510.Although a city block 510 is shown if FIG. 5, other geographicalman-made constructs might similarly apply, such constructs including,but not limited to, suburban sub-divisions, town centers, downtowndistricts, up-town districts, towns, villages, neighborhoods, and/or thelike (collectively referred to herein as “city block” for simplicity ofillustration). In some embodiments, a city block 510 might include,without limitation, one or more buildings or premises 515 which mightcomprise a home, building, business premises, commercial office, school,industrial building, etc.), one or more roadways 520 (which mightinclude, without limitation, at least one of a local road, a main road,a highway, an airport apron, an airport ramp, an airport runway, acanal, a lock, or a waterway, and/or the like), one or more lane markers525, one or more pathways 530, one or more traffic control signaldevices 535, one or more roadway street lights 540, one or more sidewalkor pedestrian street lights 545, one or more roadway-embedded batterycharging nodes or strips 550, one or more roadway-embedded powergeneration nodes 555, one or more roadway-embedded sensors 560, one ormore pathway-embedded sensors 565, one or more vehicles 570 which mightcomprise a car, minivan, pickup truck, a motorcycle, an all-terrainvehicle, a scooter, a police vehicle, a fire engine, an ambulance, arecreational vehicle, a semi-tractor-trailer truck, a commercial truck,a bus, a boat, a ship, a submersible, an amphibious vehicle, anairplane, a helicopter, a space vehicle, and/or the like), and/or thelike.

According to some embodiments, the one or more lane markers 525 mightcomprise one or more dynamic lane change markers. In some cases, the oneor more roadway-embedded battery charging nodes or strips 550 and theone or more roadway-embedded power generation nodes 555 mightrespectively charge batteries in electric vehicles as the vehicles aretravelling on the roadway 520 over the battery charging nodes (or whileparked) and generate electrical power from solar energy, heat orfriction energy from solar radiation or vehicle travel, and/or pressuretransduction from vehicle passage, as described in detail below. The oneor more roadway and/or pathway sensors 560 and 565, respectively, mighteach include, but is not limited to, at least one of one or moretemperature sensors, one or more light sensors (e.g., ambient lightsensors, luminosity sensors, illuminance sensors, solar light sensors,etc.), one or more humidity sensors, one or more motion sensors, one ormore structural integrity sensors, one or more pressure sensors, one ormore air quality sensors, one or more communications signal detectors,one or more seismic sensors, one or more weather station sensors, one ormore moisture sensors, one or more wind sensors, one or more particulatesensors, one or more impact sensors, one or more stress sensors, or oneor more location sensors, and/or the like.

In some embodiments, a telemetry hub 505 might interact with each of atleast one of one or more devices (e.g., the one or more lane markers525, the one or more traffic control signal devices 535, the one or moreroadway street lights 540, the one or more sidewalk or pedestrian streetlights 545, the one or more roadway-embedded battery charging nodes orstrips 550, the one or more roadway-embedded power generation nodes 555,the one or more vehicles 570, etc.) and/or sensors (the one or moreroadway-embedded sensors 560, one or more pathway-embedded sensors 565,or other sensors (e.g., those that might be embodied within one or moreof these devices or systems or embodied in stand-alone housings), etc.).

In some cases, the system as described herein may be used in adjunctintegral areas, including, but not limited to, Interstate rest stops, aweigh station, a cattle guard, a state/national park entrance, a tollbooth, median services (such as gas stations, restaurants, etc.),although these may be more prevalent on private toll ways or the like.

The following are examples of system 500 being used to in response toone or more situations. For example, in the case of one or moreobstacles in a roadway 520 and/or a pathway 530, and/or the like, thetelemetry hub 505 might receive at least first sensor data indicative of“jerk feedback.” The telemetry hub 505 might analyze the first sensordata to determine whether it contains “jerk feedback.” The sensor datathat is indicative of “jerk feedback” might comprise, withoutlimitation, accelerometer data indicating a sudden acceleration forcefrom one or more cars or one or more user devices such as a smartphones,suspension data indicating a sudden suspension jerk of one or more cars,location data indicating that one or more users and/or one or morevehicles have altered their path, steering data indicating one or moredrivers have steered their car in a different direction, lane changedata indicating one or more cars are changing lanes at a particularlocation, and/or the like. All of the “jerk-feedback” data may beassociated with location data to determine where the “jerk-feedback” wasreceived.

The telemetry hub 505 might analyze the first sensor data to determinewhether it contains “jerk feedback” and/or a pattern of “jerk feedback”in a certain geographic location. Based on a determination that thefirst sensor data comprises “jerk feedback” associated with theparticular geographic location, the telemetry hub 505 might determineone or more first actions to be taken in response to receiving the jerkfeedback from the at least one first user device. These one or moresecond actions might include, without limitation, determining whetherthe telemetry hub is receiving jerk feedback from more than one devicein a particular location, generating a notification indicating ageographic location where the jerk feedback occurred, sending anotification indicating a geographic location where the jerk feedbackoccurred, displaying a map on one or more client devices indicating ageographic location where the jerk feedback occurred, causing one ormore GPS systems to redirect vehicle traffic and/or pedestrian trafficaround the one or more obstacles, and/or the like. The telemetry hub 505might analyze the jerk feedback data in real-time to provide up to datedata to one or more client devices requesting the jerk feedback data. Inthis way, one or more client devices requesting the jerk feedback datamay steer one or more users around one or more obstacles in a particulargeographic location.

Further, because the telemetry hub 505 is analyzing the jerk feedbackdata in real-time, the telemetry hub 505 might further determine whetherthe jerk feedback data has disappeared from a particular geographiclocation. Based on a determination that the jerk feedback hasdisappeared from the particular location, the telemetry hub 505 mightdetermine that the one or more obstacles in a roadway 520 and/or apathway 530, and/or the like have been removed.

Based on a determination that the first sensor data no longer comprises“jerk feedback” associated with the particular geographic location, thetelemetry hub 505 might determine one or more first actions to be takenin response to determining the first sensor data no longer comprises thejerk feedback from the at least one first user device. These one or moresecond actions might include, without limitation, determining whetherthe telemetry hub is no longer receiving jerk feedback from more thanone device in a particular location, generating a notificationindicating a geographic location no longer has the jerk feedback and/orthat the one or more obstacles have been removed, sending a notificationindicating a geographic location where the one or more obstacles havebeen removed, displaying a map on one or more client devices indicatinga geographic location where the one or more obstacles have been removed,causing one or more GPS systems to redirect vehicle traffic and/orpedestrian traffic back to the geographic location where the one or moreobstacles have been removed, and/or the like.

In the event of a fire, the telemetry hub 505 might receive at leastfirst sensor data indicative of a fire. The telemetry hub might analyzethe first sensor data to determine whether it contains sensor dataassociated with a fire. The sensor data that is indicative of a firemight comprise, without limitation, temperature data indicating a suddenrise in temperature, dying gasp data indicating one or more devices arelosing power, smoke data indicating one or more smoke alarms aredetecting smoke, location data indicating locations of one or moredevices, and/or the like.

In the event of a flood, the telemetry hub 505 might receive at leastfirst sensor data indicative of a flood. The telemetry hub might analyzethe first sensor data to determine whether it contains sensor dataassociated with a flood. The sensor data that is indicative of a floodmight comprise, without limitation, temperature data indicating a suddendrop in temperature, dying gasp data indicating one or more devices arelosing power, water data indicating one or more water sensors in one ormore user devices are being exposed to water, location data indicatinglocations of one or more devices, and/or the like.

In the event of a tornado, the telemetry hub 505 might receive at leastfirst sensor data indicative of a tornado. The telemetry hub mightanalyze the first sensor data to determine whether it contains sensordata associated with a tornado. The sensor data that is indicative of atornado might comprise, without limitation, temperature data indicatinga sudden drop or rise in temperature, dying gasp data indicating one ormore devices are losing power, wind data indicating one or more windsensors are detecting high winds, location data indicating locations ofone or more devices, and/or the like.

In the event of a hurricane, the telemetry hub 505 might receive atleast first sensor data indicative of a hurricane. The telemetry hubmight analyze the first sensor data to determine whether it containssensor data associated with a hurricane. The sensor data that isindicative of a hurricane might comprise, without limitation,temperature data indicating a sudden drop or rise in temperature, dyinggasp data indicating one or more devices are losing power, wind dataindicating one or more wind sensors are detecting high winds, locationdata indicating locations of one or more devices, and/or the like.

The telemetry hub 505 might analyze the first sensor data to determinewhether it contains fire data, flood data, tornado data, hurricane data,weather data, natural disaster data, and/or the like in a certaingeographic location. Based on a determination that the first sensor datacomprises fire data, flood data, tornado data, hurricane data, weatherdata, natural disaster data, and/or the like associated with theparticular geographic location, the telemetry hub 505 might determineone or more first actions to be taken in response to receiving the firedata, flood data, tornado data, hurricane data, weather data, naturaldisaster data and/or the like from the at least one first user device.These one or more first actions might include, without limitation,generating a notification indicating a geographic location where thefire, flood, tornado, weather, natural disaster, and/or the like isoccurring, sending a notification indicating a geographic location wherethe fire, flood, tornado, weather, natural disaster, and/or the like isoccurring, displaying a map on one or more client devices indicating ageographic location where the fire, flood, tornado, weather, naturaldisaster, and/or the like is occurring, displaying a path of the fire,flood, tornado, weather, natural disaster, and/or the like, causing oneor more GPS systems to redirect vehicle traffic and/or pedestriantraffic around the fire, flood, tornado, weather, natural disaster,and/or the like, and/or the like. The telemetry hub 505 might analyzethe fire data in real-time to provide up to date data to one or moreclient devices requesting the fire data, flood data, tornado data,weather data, natural disaster data, and/or the like.

In a non-limiting example, the telemetry hub 505 might use one or moredying gasp communications to track at least one of a fire event, a floodevent, a tornado event, a hurricane event, a weather event, or a naturaldisaster event, and/or the like. For example, a user device might sensethat it is losing power and send a dying gasp notification.Alternatively, one or one or more sensors of the user device might sensea sudden rise in temperature, smoke, exposure to water, and/or the like.Based on the sensor data, the user device might determine that it isabout to lose power and send a dying gasp notification. These dying gaspnotifications may be sent with location data of the user device.

The telemetry hub 505 might track the dying gasp notifications itreceives from one or more user devices and determine one or more firstactions to be taken in response to receiving the dying gaspnotifications. These one or more first actions might include, withoutlimitation, generating a notification indicating a geographic locationwhere one or more dying gasp notifications are occurring, sending anotification indicating a geographic location where the one or moredying gasp notifications are occurring, displaying a map on one or moreclient devices indicating a geographic location where one or more dyinggasp notifications are occurring, displaying a path of the one or moredying gasp notifications are, causing one or more GPS systems toredirect vehicle traffic and/or pedestrian traffic around where the oneor more dying gasp notifications are, and/or the like. In a non-limitingexample, as the one or more dying gasps occur in a particular area, thetelemetry hub might be able to track the path of a fire, flood, tornado,hurricane, weather, natural disaster, and/or the like and sendnotifications to client devices indicating the path of the fire, flood,tornado, hurricane, weather, natural disaster, and/or the like.

The telemetry hub 505 might also be used to analyze vehicle traffic onroad 520 and/or pedestrian traffic on pathway 530 over time. Thetelemetry hub 505 might receive at least first sensor data indicative oftraffic. The telemetry hub 505 might analyze the first sensor data todetermine whether it contains sensor data associated with traffic in aparticular location. The sensor data that is indicative of a trafficmight comprise, without limitation, camera data showing flow of trafficover time, camera data showing vehicles and/or pedestrians using one ormore roadways and/or pathways, vehicle data indicating routes one ormore vehicles take, pedestrian data indicating one or more routespedestrians take, location data indicating locations of one or moredevices, and/or the like.

The telemetry hub 505 might analyze the first sensor data to determinewhether it contains traffic data in a certain geographic location. Basedon a determination that the first sensor data comprises traffic dataassociated with the particular geographic location, the telemetry hub505 might determine one or more first actions to be taken in response toreceiving the traffic data from the at least one first user device.These one or more first actions might include, without limitation,generating a notification indicating a geographic location where thetraffic is occurring, sending a notification indicating a geographiclocation where the traffic is occurring, displaying a map on one or moreclient devices indicating a geographic location where the traffic isoccurring, determining whether another lane should be added to a road,determining whether a pathway should be widened, determining whether abicycle lane should be added, determining a time of day when rush houroccurs, determining one or more alternate paths to avoid rush hourtraffic, causing one or more GPS systems to redirect vehicle trafficand/or pedestrian traffic around traffic, and/or the like. The trafficdata for a particular location may be analyzed overtime and may or maynot require real-time analysis.

Although one or more obstacles, a fire, and traffic are being used asexamples of sensor input, telemetry hub 505 might receive and/or senddifferent sensor data based on different situations or events. Thesesituations might include, without limitation, at least one of a fire, acar accident, a flood, a personal injury, a medical situation, a fire, arobbery, a burglary, an intruder, pedestrian traffic, vehicle traffic,weather, natural disasters, sports event, concert, festival, and/or thelike.

FIGS. 6A-6C (collectively, “FIG. 6”) are flow diagrams illustrating amethod 600 for implementing a telemetry hub that obtains sensor datafrom a plurality of sources, in accordance with various embodiments.

While the techniques and procedures are depicted and/or described in acertain order for purposes of illustration, it should be appreciatedthat certain procedures may be reordered and/or omitted within the scopeof various embodiments. Moreover, while the method 600 illustrated byFIG. 6 can be implemented by or with (and, in some cases, are describedbelow with respect to) the systems, examples, or embodiments 100, 200,300, 400, and 500 of FIGS. 1, 2, 3, 4, and 5, respectively (orcomponents thereof), such methods may also be implemented using anysuitable hardware (or software) implementation. Similarly, while each ofthe systems, examples, or embodiments 100, 200, 300, 400, and 500 ofFIGS. 1, 2, 3, 4, and 5, respectively (or components thereof), canoperate according to the method 600 illustrated by FIG. 6 (e.g., byexecuting instructions embodied on a computer readable medium), thesystems, examples, or embodiments 100, 200, 300, 400, and 500 of FIGS.1, 2, 3, 4, and 5 can each also operate according to other modes ofoperation and/or perform other suitable procedures.

In the non-limiting embodiment of FIG. 6A, method 600, at block 602,might comprise receiving, with a telemetry hub, first sensor data fromone or more sensors associated with one or more first user devices. Insome embodiments, the telemetry hub might receive a plurality of sensordata from a plurality of different first user devices. In some cases,the telemetry hub might include the computing system.

In some embodiments, the computing system might include, withoutlimitation, one of a data collection system, a real-time processingsystem, an artificial intelligence (“AI”) system, a data disseminationsystem, a named data system, a server computer, a cloud-based computingsystem over a network, or a distributed computing system, and/or thelike. In some cases, the one or more first user devices, withoutlimitation, includes one or more network nodes, one or more serviceprovider devices, one or more laptop computers, one or more desktopcomputers, one or more tablet computers, one or more television sets,one or more smart televisions, one or more media players, one or moregaming consoles, one or more set-top boxes (“STBs”), one or more digitalvideo recording (“DVR”) devices, one or more smart phones, one or moremobile phones, or one or more personal digital assistants, and/or thelike. The one or more sensors might include, but are not limited to, oneor more accelerometers, one or more thermometers, one or more air flowsensors, one or more light sensors, one or more wind sensors, one ormore weather station sensors, one or more wave sensors, one or moremotion detectors, one or more humidity sensors, one or more smokedetectors, one or more gas detection sensors, one or more biometricsensors, one or more health sensors, one or more heartbeat sensors, oneor more impact sensors, one or more cameras, or one or more locationsensors, and/or the like.

At block 604, method 600 might comprise, determining, with a computingsystem, whether the first sensor data can be trusted. If not, method 600might continue to the process at optional block 606. If so, the method600 might proceed to the process at block 610. At optional block 606,method 600 might comprise, based on a determination that the firstsensor data requires further analysis to determine whether the firstsensor data can be trusted, sending, with the computing system and to ablockchain system, a request for identifying a blockchain containing ablock containing a copy of the first sensor data that is output by theone or more first user devices. Next, method 600, at optional block 608might continue by analyzing, with at least one of the computing systemor the blockchain system, the first sensor data by performing sourceidentification on the first sensor data. The first sensor data mightinclude source identification information and performing sourceidentification on the first sensor data might include determining thesource identification information contained in the first sensor data anddetermining whether the source identification information contained inthe first sensor data can be trusted.

At block 610, method 600 might comprise, based on a determination thatthe first sensor data can be trusted, validating, with the computingsystem, the first sensor data from the one or more sensors. Thecomputing system might determine whether the first sensor data from theone or more sensors is accurate. In order to validate the first sensordata, the computing system might compare the first sensor data withother sensor data within a geographic region and might determine whetherthe first sensor data matches or is close to the other sensor datawithin the same geographic region. Additionally and/or alternatively,based on a determination that the one or more first user devicestypically or historically provide accurate data, the computing systemmight determine that the first sensor data is accurate.

Method 600 might further comprise, based on a determination that thefirst sensor data is valid, analyzing, with the computing system, thefirst sensor data to determine one or more first actions to take inresponse to receiving the first sensor data from the one or more userdevices (block 612). The first sensor data may be analyzed in real-timeor near real-time. Analyzing the first sensor data might includedifferent steps as shown in FIG. 6B. In some embodiments, method 600, atblock 614, might comprise implementing, with the computing system, theone or more first actions based at least in part on the analysis of thefirst sensor data. Implementing the one or more first actions mightinclude different steps as shown in FIG. 6C.

In some embodiments, analyzing the first sensor data to determine one ormore first actions to take in response to receiving the first sensordata from the one or more user devices (at block 612) might comprisedetermining, with the computing system, a geographic location associatedwith the first sensor data (optional block 616) and, based on adetermination of the geographic location associated with the firstsensor data, determining one or more first actions to take in responseto receiving the first sensor data from the geographic location(optional block 618).

Alternatively, analyzing the first sensor data to determine one or morefirst actions to take in response to receiving the first sensor datafrom the one or more user devices (at block 612) might compriseanalyzing, with the computing system, the first sensor data to determinewhether the first sensor data comprises jerk feedback associated with aparticular geographic location (optional block 620). At optional block622, method 600 might comprise, based on a determination that the firstsensor data comprises jerk feedback associated with the particulargeographic location, determining one or more second actions to be takenin response to receiving the jerk feedback from the at least one firstuser device. Next, at optional block 624, method 600 might includegenerating a notification indicating a geographic location where thejerk feedback occurred. Method 600, at optional block 626, might alsoinclude sending, with the computing device, the notification to one ormore user devices located within the geographic location where the jerkfeedback occurred.

According to some embodiments, implementing the one or more firstactions based at least in part on the analysis of the first sensor data(at block 614) might comprise identifying, with the computing system, atleast one user to receive the first sensor data (optional block 628) andsending, with the computing system, the first sensor data to one or moresecond user devices associated with the at least one user identified bythe computing system (optional block 630).

Alternatively, or additionally, implementing the one or more firstactions based at least in part on the analysis of the first sensor data(at block 614) might comprise determining, with the computing device,whether the first sensor data from the one or more first user devices isrelated to second sensor data from one or more second user devices(optional block 632). Method 600, at optional block 634, might comprise,based on a determination that the first sensor data from the one or morefirst user devices is related to the second sensor data from the one ormore second user devices, associating, with the computing system, thefirst sensor data from the one or more first user devices with thesecond sensor data from the one or more second user devices. The firstsensor data may be associated with the second sensor data based on acommon geographic location associated with the first sensor data and thesecond sensor data, a common time associated with the first sensor dataand the second sensor data, and/or the like.

Additionally and/or alternatively, method 600 might comprise generating,with the computing system, a profile with the first sensor data and thesecond sensor data (optional block 636) and might comprise displaying,with the computing system, the profile with the first sensor data andthe second sensor data on one or more second user devices (optionalblock 638). The profile may display, without limitation, at least one ofvehicle traffic in one or more geographic locations, pedestrian trafficin one or more geographic locations, one or more obstacles located inone or more geographic locations, natural disasters in one or moregeographic locations, or one or more weather paths, and/or the like.

Alternatively, or additionally, implementing the one or more firstactions based at least in part on the analysis of the first sensor data(at block 614) might comprise determining, with the computing system, atime sensitivity associated with the first sensor data (optional block640), based on a determination that the first sensor data is timesensitive, determining, with the computing system, a first amount oftime to store the first sensor data (optional block 642), and based on adetermination that the first sensor data is not time sensitive,determining, with the computing system, a second amount of time to storethe first sensor data (optional block 644).

Exemplary System and Hardware Implementation

FIG. 7 is a block diagram illustrating an exemplary computer or systemhardware architecture, in accordance with various embodiments. FIG. 7provides a schematic illustration of one embodiment of a computer system700 of the service provider system hardware that can perform the methodsprovided by various other embodiments, as described herein, and/or canperform the functions of computer or hardware system (i.e., telemetryhubs 105, 305, 405, and 505, computing systems 115 and 315, user devices125 a-125 n, 325 a-325 n, and 415, client devices 135 a-135 n, 335 a-335n, blockchain systems 150, or blockchain computing system 155, etc.), asdescribed above. It should be noted that FIG. 7 is meant only to providea generalized illustration of various components, of which one or more(or none) of each may be utilized as appropriate. FIG. 7, therefore,broadly illustrates how individual system elements may be implemented ina relatively separated or relatively more integrated manner.

The computer or hardware system 700—which might represent an embodimentof the computer or hardware system (i.e., telemetry hubs 105, 305, 405,and 505, computing systems 115 and 315, user devices 125 a-125 n, 325a-325 n, and 415, client devices 135 a-135 n, 335 a-335 n, blockchainsystems 150, or blockchain computing system 155, etc.), described abovewith respect to FIGS. 1-6—is shown comprising hardware elements that canbe electrically coupled via a bus 705 (or may otherwise be incommunication, as appropriate). The hardware elements may include one ormore processors 710, including, without limitation, one or moregeneral-purpose processors and/or one or more special-purpose processors(such as microprocessors, digital signal processing chips, graphicsacceleration processors, and/or the like); one or more input devices715, which can include, without limitation, a mouse, a keyboard, and/orthe like; and one or more output devices 720, which can include, withoutlimitation, a display device, a printer, and/or the like.

The computer or hardware system 700 may further include (and/or be incommunication with) one or more storage devices 725, which can comprise,without limitation, local and/or network accessible storage, and/or caninclude, without limitation, a disk drive, a drive array, an opticalstorage device, solid-state storage device such as a random accessmemory (“RAM”) and/or a read-only memory (“ROM”), which can beprogrammable, flash-updateable, and/or the like. Such storage devicesmay be configured to implement any appropriate data stores, including,without limitation, various file systems, database structures, and/orthe like.

The computer or hardware system 700 might also include a communicationssubsystem 730, which can include, without limitation, a modem, a networkcard (wireless or wired), an infra-red communication device, a wirelesscommunication device and/or chipset (such as a Bluetooth™ device, an802.11 device, a WiFi device, a WiMax device, a WWAN device, cellularcommunication facilities, etc.), and/or the like. The communicationssubsystem 730 may permit data to be exchanged with a network (such asthe network described below, to name one example), with other computeror hardware systems, and/or with any other devices described herein. Inmany embodiments, the computer or hardware system 700 will furthercomprise a working memory 735, which can include a RAM or ROM device, asdescribed above.

The computer or hardware system 700 also may comprise software elements,shown as being currently located within the working memory 735,including an operating system 740, device drivers, executable libraries,and/or other code, such as one or more application programs 745, whichmay comprise computer programs provided by various embodiments(including, without limitation, hypervisors, VMs, and the like), and/ormay be designed to implement methods, and/or configure systems, providedby other embodiments, as described herein. Merely by way of example, oneor more procedures described with respect to the method(s) discussedabove might be implemented as code and/or instructions executable by acomputer (and/or a processor within a computer); in an aspect, then,such code and/or instructions can be used to configure and/or adapt ageneral purpose computer (or other device) to perform one or moreoperations in accordance with the described methods.

A set of these instructions and/or code might be encoded and/or storedon a non-transitory computer readable storage medium, such as thestorage device(s) 725 described above. In some cases, the storage mediummight be incorporated within a computer system, such as the system 700.In other embodiments, the storage medium might be separate from acomputer system (i.e., a removable medium, such as a compact disc,etc.), and/or provided in an installation package, such that the storagemedium can be used to program, configure, and/or adapt a general purposecomputer with the instructions/code stored thereon. These instructionsmight take the form of executable code, which is executable by thecomputer or hardware system 700 and/or might take the form of sourceand/or installable code, which, upon compilation and/or installation onthe computer or hardware system 700 (e.g., using any of a variety ofgenerally available compilers, installation programs,compression/decompression utilities, etc.) then takes the form ofexecutable code.

It will be apparent to those skilled in the art that substantialvariations may be made in accordance with specific requirements. Forexample, customized hardware (such as programmable logic controllers,field-programmable gate arrays, application-specific integratedcircuits, and/or the like) might also be used, and/or particularelements might be implemented in hardware, software (including portablesoftware, such as applets, etc.), or both. Further, connection to othercomputing devices such as network input/output devices may be employed.

As mentioned above, in one aspect, some embodiments may employ acomputer or hardware system (such as the computer or hardware system700) to perform methods in accordance with various embodiments of theinvention. According to a set of embodiments, some or all of theprocedures of such methods are performed by the computer or hardwaresystem 700 in response to processor 710 executing one or more sequencesof one or more instructions (which might be incorporated into theoperating system 740 and/or other code, such as an application program745) contained in the working memory 735. Such instructions may be readinto the working memory 735 from another computer readable medium, suchas one or more of the storage device(s) 725. Merely by way of example,execution of the sequences of instructions contained in the workingmemory 735 might cause the processor(s) 710 to perform one or moreprocedures of the methods described herein.

The terms “machine readable medium” and “computer readable medium,” asused herein, refer to any medium that participates in providing datathat causes a machine to operate in a specific fashion. In an embodimentimplemented using the computer or hardware system 700, various computerreadable media might be involved in providing instructions/code toprocessor(s) 710 for execution and/or might be used to store and/orcarry such instructions/code (e.g., as signals). In manyimplementations, a computer readable medium is a non-transitory,physical, and/or tangible storage medium. In some embodiments, acomputer readable medium may take many forms, including, but not limitedto, non-volatile media, volatile media, or the like. Non-volatile mediaincludes, for example, optical and/or magnetic disks, such as thestorage device(s) 725. Volatile media includes, without limitation,dynamic memory, such as the working memory 735. In some alternativeembodiments, a computer readable medium may take the form oftransmission media, which includes, without limitation, coaxial cables,copper wire, and fiber optics, including the wires that comprise the bus705, as well as the various components of the communication subsystem730 (and/or the media by which the communications subsystem 730 providescommunication with other devices). In an alternative set of embodiments,transmission media can also take the form of waves (including withoutlimitation radio, acoustic, and/or light waves, such as those generatedduring radio-wave and infra-red data communications).

Common forms of physical and/or tangible computer readable mediainclude, for example, a floppy disk, a flexible disk, a hard disk,magnetic tape, or any other magnetic medium, a CD-ROM, any other opticalmedium, punch cards, paper tape, any other physical medium with patternsof holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chipor cartridge, a carrier wave as described hereinafter, or any othermedium from which a computer can read instructions and/or code.

Various forms of computer readable media may be involved in carrying oneor more sequences of one or more instructions to the processor(s) 710for execution. Merely by way of example, the instructions may initiallybe carried on a magnetic disk and/or optical disc of a remote computer.A remote computer might load the instructions into its dynamic memoryand send the instructions as signals over a transmission medium to bereceived and/or executed by the computer or hardware system 700. Thesesignals, which might be in the form of electromagnetic signals, acousticsignals, optical signals, and/or the like, are all examples of carrierwaves on which instructions can be encoded, in accordance with variousembodiments of the invention.

The communications subsystem 730 (and/or components thereof) generallywill receive the signals, and the bus 705 then might carry the signals(and/or the data, instructions, etc. carried by the signals) to theworking memory 735, from which the processor(s) 705 retrieves andexecutes the instructions. The instructions received by the workingmemory 735 may optionally be stored on a storage device 725 eitherbefore or after execution by the processor(s) 710.

As noted above, a set of embodiments comprises methods and systems forimplementing a telemetry hub, and, more particularly, to methods,systems, and apparatuses for implementing a telemetry hub that obtainssensor data from a plurality of sources and that determines one or morefirst actions to take in response to receiving the first sensor datafrom the plurality of sources. FIG. 8 illustrates a schematic diagram ofa system 800 that can be used in accordance with one set of embodiments.The system 800 can include one or more user computers, user devices, orcustomer devices 805. A user computer, user device, or customer device805 can be a general purpose personal computer (including, merely by wayof example, desktop computers, tablet computers, laptop computers,handheld computers, and the like, running any appropriate operatingsystem, several of which are available from vendors such as Apple,Microsoft Corp., and the like), cloud computing devices, a server(s),and/or a workstation computer(s) running any of a variety ofcommercially-available UNIX™ or UNIX-like operating systems. A usercomputer, user device, or customer device 805 can also have any of avariety of applications, including one or more applications configuredto perform methods provided by various embodiments (as described above,for example), as well as one or more office applications, databaseclient and/or server applications, and/or web browser applications.Alternatively, a user computer, user device, or customer device 805 canbe any other electronic device, such as a thin-client computer,Internet-enabled mobile telephone, and/or personal digital assistant,capable of communicating via a network (e.g., the network(s) 810described below) and/or of displaying and navigating web pages or othertypes of electronic documents. Although the exemplary system 800 isshown with two user computers, user devices, or customer devices 805,any number of user computers, user devices, or customer devices can besupported.

Certain embodiments operate in a networked environment, which caninclude a network(s) 810. The network(s) 810 can be any type of networkfamiliar to those skilled in the art that can support datacommunications using any of a variety of commercially-available (and/orfree or proprietary) protocols, including, without limitation, TCP/IP,SNA™, IPX™, AppleTalk™, and the like. Merely by way of example, thenetwork(s) 810 (similar to network(s) 140, 160, 340 of FIGS. 1 and 3, orthe like) can each include a local area network (“LAN”), including,without limitation, a fiber network, an Ethernet network, a Token-Ring™network, and/or the like; a wide-area network (“WAN”); a wireless widearea network (“WWAN”); a virtual network, such as a virtual privatenetwork (“VPN”); the Internet; an intranet; an extranet; a publicswitched telephone network (“PSTN”); an infra-red network; a wirelessnetwork, including, without limitation, a network operating under any ofthe IEEE 802.11 suite of protocols, the Bluetooth™ protocol known in theart, and/or any other wireless protocol (e.g., LTE protocol, 5Gprotocol, LoRa protocol, etc.); and/or any combination of these and/orother networks. In a particular embodiment, the network might include anaccess network of the service provider (e.g., an Internet serviceprovider (“ISP”)). In another embodiment, the network might include acore network of the service provider, and/or the Internet.

Embodiments can also include one or more server computers 815. Each ofthe server computers 815 may be configured with an operating system,including, without limitation, any of those discussed above, as well asany commercially (or freely) available server operating systems. Each ofthe servers 815 may also be running one or more applications, which canbe configured to provide services to one or more clients 805 and/orother servers 815.

Merely by way of example, one of the servers 815 might be a data server,a web server, a cloud computing device(s), or the like, as describedabove. The data server might include (or be in communication with) a webserver, which can be used, merely by way of example, to process requestsfor web pages or other electronic documents from user computers 805. Theweb server can also run a variety of server applications, including HTTPservers, FTP servers, CGI servers, database servers, Java servers, andthe like. In some embodiments of the invention, the web server may beconfigured to serve web pages that can be operated within a web browseron one or more of the user computers 805 to perform methods of theinvention.

The server computers 815, in some embodiments, might include one or moreapplication servers, which can be configured with one or moreapplications accessible by a client running on one or more of the clientcomputers 805 and/or other servers 815. Merely by way of example, theserver(s) 815 can be one or more general purpose computers capable ofexecuting programs or scripts in response to the user computers 805and/or other servers 815, including, without limitation, webapplications (which might, in some cases, be configured to performmethods provided by various embodiments). Merely by way of example, aweb application can be implemented as one or more scripts or programswritten in any suitable programming language, such as Java™, C, C#™ orC++, and/or any scripting language, such as Perl, Python, or TCL, aswell as combinations of any programming and/or scripting languages. Theapplication server(s) can also include database servers, including,without limitation, those commercially available from Oracle™,Microsoft™, Sybase™, IBM™, and the like, which can process requests fromclients (including, depending on the configuration, dedicated databaseclients, API clients, web browsers, etc.) running on a user computer,user device, or customer device 805 and/or another server 815. In someembodiments, an application server can perform one or more of theprocesses for implementing a telemetry hub, and, more particularly, tomethods, systems, and apparatuses for implementing a telemetry hub thatobtains sensor data from a plurality of sources and that determines oneor more first actions to take in response to receiving the first sensordata from the plurality of sources, as described in detail above. Dataprovided by an application server may be formatted as one or more webpages (comprising HTML, JavaScript, etc., for example) and/or may beforwarded to a user computer 805 via a web server (as described above,for example). Similarly, a web server might receive web page requestsand/or input data from a user computer 805 and/or forward the web pagerequests and/or input data to an application server. In some cases, aweb server may be integrated with an application server.

In accordance with further embodiments, one or more servers 815 canfunction as a file server and/or can include one or more of the files(e.g., application code, data files, etc.) necessary to implementvarious disclosed methods, incorporated by an application running on auser computer 805 and/or another server 815. Alternatively, as thoseskilled in the art will appreciate, a file server can include allnecessary files, allowing such an application to be invoked remotely bya user computer, user device, or customer device 805 and/or server 815.

It should be noted that the functions described with respect to variousservers herein (e.g., application server, database server, web server,file server, etc.) can be performed by a single server and/or aplurality of specialized servers, depending on implementation-specificneeds and parameters.

In certain embodiments, the system can include one or more databases 820a-820 n (collectively, “databases 820”). The location of each of thedatabases 820 is discretionary: merely by way of example, a database 820a might reside on a storage medium local to (and/or resident in) aserver 815 a (and/or a user computer, user device, or customer device805). Alternatively, a database 820 n can be remote from any or all ofthe computers 805, 815, so long as it can be in communication (e.g., viathe network 810) with one or more of these. In a particular set ofembodiments, a database 820 can reside in a storage-area network (“SAN”)familiar to those skilled in the art. (Likewise, any necessary files forperforming the functions attributed to the computers 805, 815 can bestored locally on the respective computer and/or remotely, asappropriate.) In one set of embodiments, the database 820 can be arelational database, such as an Oracle database, that is adapted tostore, update, and retrieve data in response to SQL-formatted commands.The database might be controlled and/or maintained by a database server,as described above, for example.

According to some embodiments, system 800 might further comprise acomputing system 825 and corresponding database(s) 830 (similar totelemetry hub 105 and corresponding database 110, computing system(s)115 and corresponding database(s) 120, telemetry hub 405, and/ortelemetry hub 505, of FIGS. 1, 3, 4, and 5, or the like). System 800might further comprise one or more user devices 835 (similar to userdevices 130 a-130 n, 330 a-330 n, and 420 of FIGS. 1, 3, and 4, or thelike) comprising one or more sensors 840 (similar to sensors 125 a-125n, 325 a-325 n, and 415 of FIGS. 1, 3, and 4, or the like). System 800might also include one or more client devices 845 (similar to clientdevices 135 a-135 n and 335 a-335 n of FIGS. 1 and 3, or the like).

In operation, computing system 825 might receive first sensor data fromone or more sensors 840 associated with one or more first user devices835. Next, the computing system 825 might determine whether the firstsensor data can be trusted. Based on a determination that the firstsensor data can be trusted, the computing system 825 might validate thefirst sensor data from the one or more sensors 840. Based on adetermination that the first sensor data is valid, the computing system825 might analyze the first sensor data to determine one or more firstactions to take in response to receiving the first sensor data from theone or more user devices 835. Next, the computing system 825 mightimplement the one or more first actions based at least in part on theanalysis of the first sensor data. These one or more actions mightinclude sending the first sensor data to a client device(s) 845.

These and other functions of the system 800 (and its components) aredescribed in greater detail above with respect to FIGS. 1-6.

While certain features and aspects have been described with respect toexemplary embodiments, one skilled in the art will recognize thatnumerous modifications are possible. For example, the methods andprocesses described herein may be implemented using hardware components,software components, and/or any combination thereof. Further, whilevarious methods and processes described herein may be described withrespect to particular structural and/or functional components for easeof description, methods provided by various embodiments are not limitedto any particular structural and/or functional architecture but insteadcan be implemented on any suitable hardware, firmware and/or softwareconfiguration. Similarly, while certain functionality is ascribed tocertain system components, unless the context dictates otherwise, thisfunctionality can be distributed among various other system componentsin accordance with the several embodiments.

Moreover, while the procedures of the methods and processes describedherein are described in a particular order for ease of description,unless the context dictates otherwise, various procedures may bereordered, added, and/or omitted in accordance with various embodiments.Moreover, the procedures described with respect to one method or processmay be incorporated within other described methods or processes;likewise, system components described according to a particularstructural architecture and/or with respect to one system may beorganized in alternative structural architectures and/or incorporatedwithin other described systems. Hence, while various embodiments aredescribed with—or without—certain features for ease of description andto illustrate exemplary aspects of those embodiments, the variouscomponents and/or features described herein with respect to a particularembodiment can be substituted, added and/or subtracted from among otherdescribed embodiments, unless the context dictates otherwise.Consequently, although several exemplary embodiments are describedabove, it will be appreciated that the invention is intended to coverall modifications and equivalents within the scope of the followingclaims.

What is claimed is:
 1. A method, comprising: receiving, with a telemetryhub, first sensor data from one or more sensors associated with one ormore first user devices; determining, with a computing system, whetherthe first sensor data can be trusted; based on a determination that thefirst sensor data can be trusted, validating, with the computing system,the first sensor data from the one or more sensors; based on adetermination that the first sensor data is valid, analyzing, with thecomputing system, the first sensor data to determine one or more firstactions to take in response to receiving the first sensor data from theone or more user devices; implementing, with the computing system, theone or more first actions based at least in part on the analysis of thefirst sensor data; analyzing, with at least one of the computing systemor the blockchain system, the first sensor data by performing sourceidentification on the first sensor data, wherein the first sensor datacomprises source identification information, wherein performing sourceidentification on the first sensor data comprises determining the sourceidentification information contained in the first sensor data can betrusted.
 2. The method of claim 1, wherein the telemetry hub comprisesthe computing system.
 3. The method of claim 1, wherein the computingsystem comprises one of a data collection system, a real-time processingsystem, an artificial intelligence (“AI”) system, a server computer, acloud-based computing system over a network, or a distributed computingsystem.
 4. The method of claim 1, wherein the one or more first userdevices comprises one or more network nodes, one or more serviceprovider devices, one or more laptop computers, one or more desktopcomputers, one or more tablet computers, one or more television sets,one or more smart televisions, one or more media players, one or moregaming consoles, one or more set-top boxes (“STBs”), one or more digitalvideo recording (“DVR”) devices, one or more smart phones, one or moremobile phones, or one or more personal digital assistants.
 5. The methodof claim 1, wherein the one or more sensors comprise one or moreaccelerometers, one or more thermometers, one or more air flow sensors,one or more light sensors, one or more wind sensors, one or more weatherstation sensors, one or more wave sensors, one or more motion detectors,one or more humidity sensors, one or more smoke detectors, one or moregas detection sensors, one or more biometric sensors, one or more healthsensors, one or more heartbeat sensors, one or more impact sensors, oneor more cameras, or one or more location sensors.
 6. The method of claim1, further comprising: based on a determination that the first sensordata requires further analysis to determine whether the first sensordata can be trusted, sending, with the computing system and to ablockchain system, a request for identifying a blockchain containing ablock containing a copy of the first sensor data that is output by theone or more first user devices.
 7. The method of claim 1, whereinanalyzing the first sensor data comprises analyzing, with the computingsystem, the first sensor data in real-time or near-real-time.
 8. Themethod of claim 1, wherein analyzing the first sensor data comprises:determining, with the computing system, a geographic location associatedwith the first sensor data; and based on a determination of thegeographic location associated with the first sensor data, determiningone or more second actions to take in response to receiving the firstsensor data from the geographic location.
 9. The method of claim 1,wherein the first sensor data comprises at least one of datacommunicated by third party service provider systems, data communicatedby public service systems, or public data, wherein the data communicatedby public service systems comprises at least one of data communicated bytransportation systems, data communicated by delivery systems, or datacommunicated by emergency response systems, and wherein the public datacomprises at least one of data communicated by weather systems, datacommunicated by user devices, or data communicated by traffic systems.10. The method of claim 1, wherein the one or more first actionscomprise: identifying, with the computing system, at least one user toreceive the first sensor data; and sending, with the computing system,the first sensor data to one or more second user devices associated withthe at least one user identified by the computing system.
 11. The methodof claim 1, wherein the one or more first actions comprise: determining,with the computing device, whether the first sensor data from the one ormore first user devices is related to second sensor data from one ormore second user devices; and based on a determination that the firstsensor data from the one or more first user devices is related to thesecond sensor data from the one or more second user devices,associating, with the computing system, the first sensor data from theone or more first user devices with the second sensor data from the oneor more second user devices.
 12. The method of claim 11, wherein thefirst sensor data is associated with the second sensor data based on acommon geographic location associated with the first sensor data and thesecond sensor data.
 13. The method of claim 11, further comprising:generating, with the computing system, a profile with the first sensordata and the second sensor data; and displaying, with the computingsystem, the profile with the first sensor data and the second sensordata on one or more third user devices.
 14. The method of claim 13,wherein the profile displays at least one of vehicle traffic in one ormore geographic locations, pedestrian traffic in one or more geographiclocations, one or more obstacles located in one or more geographiclocations, natural disasters in one or more geographic locations, or oneor more weather paths.
 15. The method of claim 1, wherein the one ormore first actions comprise: determining, with the computing system, atime sensitivity associated with the first sensor data; based on adetermination that the first sensor data is time sensitive, determining,with the computing system, a first amount of time to store the firstsensor data; and based on a determination that the first sensor data isnot time sensitive, determining, with the computing system, a secondamount of time to store the first sensor data.
 16. The method of claim1, wherein analyzing the first sensor data to determine one or morefirst actions to be taken in response to receiving the first sensor datafrom the at least one first user device further comprises: analyzing,with the computing system, the first sensor data to determine whetherthe first sensor data comprises jerk feedback associated with aparticular geographic location; based on a determination that the firstsensor data comprises jerk feedback associated with the particulargeographic location, determining one or more second actions to be takenin response to receiving the jerk feedback from the at least one firstuser device; generating a notification indicating a geographic locationwhere the jerk feedback occurred; and sending, with the computingdevice, the notification to one or more user devices located within thegeographic location where the jerk feedback occurred.
 17. An apparatus,comprising: at least one processor; and a non-transitory computerreadable medium communicatively coupled to the at least one processor,the non-transitory computer readable medium having stored thereoncomputer software comprising a set of instructions that, when executedby the at least one processor, causes the apparatus to: receive firstsensor data from one or more sensors associated with one or more firstuser devices; determine whether the first sensor data can be trusted;based on a determination that the first sensor data can be trusted,validate the first sensor data from the one or more sensors; based on adetermination that the first sensor data is valid, analyze the firstsensor data to determine one or more first actions to take in responseto receiving the first sensor data from the one or more user devices;implement the one or more first actions based at least in part on theanalysis of the first sensor data; and analyze the first sensor data byperforming source identification on the first sensor data, wherein thefirst sensor data comprises source identification information, whereinperforming source identification on the first sensor data comprisesdetermining the source identification information contained in the firstsensor data can be trusted.
 18. A system, comprising: a first userdevice comprising: at least one first processor; and a firstnon-transitory computer readable medium communicatively coupled to theat least one first processor, the first non-transitory computer readablemedium having stored thereon computer software comprising a first set ofinstructions that, when executed by the at least one processor, causesthe first user device to: receive sensor data from one or more sensorsassociated with the first user device; and send the sensor data to atelemetry hub; the telemetry hub comprising: at least one secondprocessor; and a second non-transitory computer readable mediumcommunicatively coupled to the at least one second processor, the secondnon-transitory computer readable medium having stored thereon computersoftware comprising a second set of instructions that, when executed bythe at least one second processor, causes the telemetry hub to: receivethe first sensor data from the first user device; and send the firstsensor data to a computing system; the computing system comprising: atleast one third processor; and a third non-transitory computer readablemedium communicatively coupled to the at least one third processor, thethird non-transitory computer readable medium having stored thereoncomputer software comprising a third set of instructions that, whenexecuted by the at least one third processor, causes the computingsystem to: determine whether the first sensor data can be trusted; basedon a determination that the first sensor data can be trusted, validatethe first sensor data from the one or more sensors; based on adetermination that the first sensor data is valid, analyze the firstsensor data to determine one or more first actions to take in responseto receiving the first sensor data from the one or more user devices;implement the one or more first actions based at least in part on theanalysis of the first sensor data; and analyze the first sensor data byperforming source identification on the first sensor data, wherein thefirst sensor data comprises source identification information, whereinperforming source identification on the first sensor data comprisesdetermining the source identification information contained in the firstsensor data can be trusted.